Processing sensitive information over voip

ABSTRACT

The invention relates to a method of processing sensitive information over VoIP. The method provides a method of processing, by a call processor, a media call comprising the steps of: receiving a first signalling stream from a first entity; creating a second signalling stream to a second entity; forwarding signals received from the first signalling stream to the second signalling stream; receiving a third signalling stream from the second entity; creating a fourth signalling stream to the first entity; and forwarding signals received on the third signalling stream to the fourth signalling stream; the first signalling stream containing instructions to set up a media call between the first entity and the second entity such that media is transmitted over a first media stream from the first entity to the second entity and a media is transmitted over a second media stream from the second entity to the first entity without intervention by said call processor.

BACKGROUND a. Field of the Invention

Contact centres are extensively used by service providers for deliveringservices to, and communicating with, customers. Contact centrestypically comprise a large group of agents taking or making telephonecalls with customers. Contact centres often use call recordingtechnologies, where an audio recording of the customer conversation isstored, and/or screen recording technologies, where a video or staticsnapshot of the agent's computer terminal is stored in order to aid instaff training, customer complaint management, compliance monitoring orrecord-keeping.

In many contact centre transactions the customer is either required toconfirm his identity by providing the answer to security-basedquestions, or to provide his payment card details to pay for atransaction. The nature of much of this information is highly sensitive.In particular, the information can include passwords,personally-identifiable information such as a date of birth, a PIN, amemorable phrase, bank account numbers, credit card security codes andthe like.

Data and identity theft, as well as fraudulent financial transactions,are widespread, and so it is of particular interest to the caller tokeep secret as much of the information as possible. Disclosingpersonally-sensitive financial or other security information to acontact centre agent has the potential to increase personal data loss ina number of ways. For example, the contact centre agent can write downor memorise the customer's information for later use. It has even beenknown for agent's to make their own personal recordings of theinformation using their personal mobile phones or devices.

Furthermore, where audio or video recordings or screen shots arerecorded, such data is vulnerable to fraudulent access.

The Payment Card Industry (“PCI”) has developed a Data Security Standard(DSS) for businesses that store, process and/or transmit credit carddata. Compliance with the PCI security standards is not optional forsuch businesses. The DSS dictates the methods and ways in whichcompanies processing credit card data (including telephone-based creditcard transactions) can store card and personal data. Regulations andguidelines such as these have a direct impact on contact centre whichtake customers' sensitive data in telephone conversations.

Secure telephony payment systems have been developed which can be usedin order to allow potentially sensitive information such as payment cardinformation to be transmitted directly to a payment processing systemwhilst preventing such information being transmitted in any form to thecontact centres agent or contact centre agent terminal. In general acall is routed via the secure system and the system uses one of a numberof various techniques such as suppression of Dual Tone Multi Frequency(DTMF) tones or muting the caller's voice stream in order to preventpotentially sensitive data from reaching the contact centre.

Contact centres have complex telephony systems optimised to provide bulkrouting of calls at minimum cost. The majority of calls into the contactcentre may not typically contain sensitive information, but it isimportant for the contact centre to be able to handle sensitiveinformation securely should the need arise during any call handled bythe contact centre staff. It is therefore desirable, but more expensive,to route all calls through the secure telephony system prior to entryinto the contact centre. As the proportion of an individual callactually containing the sensitive information is small compared to thetotal length of the call it is not desirable or cost effective to usethe secure telephony payment system for the entire duration of the call.

Ideally the secure telephony payment system would only be utilised forthe relatively short period of time whilst secure information is beingrelayed to the payment processing system, but would be available for useby other transactions once the part of the call requiring transmissionof secure information is complete.

However, it is problematic to switch a secure telephony payment systemin and out of the call path once the call has been received by an agentin the contact centre. The process typically involves terminating thecall and the contact centre agent calling back the original caller on asecure line. Alternative methods, such as creating a conference callwith the secure payment system are ineffective as the sensitive datawill still be detectable within the contact centre telephony system andtherefore the advantage of removing the sensitive data from the contactcentre is lost. Processes to place the caller ‘on hold’ within thepublic telephony system (i.e. external to the contact centre) whilst thecontact centre agent is disconnected and reconnected via the securepayment system are also typically problematic as, for efficiency, inmost contact centre systems when a call is terminated the agent handlingthe call generally becomes free again and available for subsequentcalls. Hence the agent handling the initial call might not be availableonce the call returns to the centre via the secure payment system.

Historically calls have been routed using circuit switched connectionsin the public switched telephone network (PSTN). A caller would call thecontact centre via the PSTN and the call centre private branch exchange(PBX) and the Automatic Call Distribution (ACD) system would connect thecaller to an agent. All signalling was transmitted over the voicechannel and the signalling and voice were very much bound together.

However, with the advent of Voice over Internet Protocol (VoIP)technologies signalling and voice are generally transmitted usingdifferent protocols from one another. VoIP isn't a protocol itself.Rather, VoIP is an umbrella term for a set of protocols involved intransporting voice information using IP. VoIP protocols include Sessioninitiation Protocol (SIP), Media Gateway Control Protocol (MGCP) andH.323, for example. Whilst VoIP protocols are not yet standardised, SIPappears to be emerging as a popular choice. For secure transmissions ofSIP messages over insecure network links, the protocol may be encryptedwith Transport Layer Security (TLS).

SIP doesn't encode audio information in a phone call, nor does ittransport audio information. SIP simply initiates and terminatescommunications sessions, for example the session may be a voice callbetween two people or a video conference between a whole team.

The job of SIP is to set up a call, conference or other interactivecommunication session and terminate it when it's over. This is achievedby sending messages between endpoints known as “SIP addresses.” SIPdoesn't do much during the session itself as its primary purpose is toestablish the session and then end it. Therefore, the bandwidth of a SIPsignalling stream is relatively small, for example, approximately 5Kbps.

The session media (for example speech/voice or image data/video) istransmitted via a separate media stream. SIP can be used in conjunctionwith various protocols that specify and carry the session media. Mediatype and parameter negotiation and media setup is performed usingSession Description Protocol (SDP), which is carried as payload in SIPmessages.

Before voice can be sent over IP, it is encoded using a voice codec toconvert audio signals into data.

The encoded packets of audio data are usually sent using Real-timeTransport Protocol (RTP) or Secure Real-time Transport Protocol (SRTP),specialised application-layer protocols for transporting audio and videodata when real-time streaming is necessary.

Signalling or media stream packets are themselves transmitted usingtransport layer protocols such as Transmission Control Protocol (TCP) orUser Datagram

Protocol (UDP). TCP is a protocol designed to transmit packets in anordered sequence and to retransmit any packets that are lost along theway. Packet headers specify the order of each packet in the sequence. Ifpackets are received out of order, they can be reordered at thereceiving end. UDP is a protocol designed to transmit data withoutretransmission of lost packets or detection of out-of-sequence packets.

UDP is better than TCP for voice streams. Lost and out-of-sequencepackets can cause audio quality issues, but usually these aren'tdetectable by the human ear. The amount of delay caused by there-ordering and retransmission of TCP packets can ultimately result inmuch worse audio quality problems. SIP signalling streams on the otherhand are usually transmitted using TCP.

Two of the most common codec standards are G.711 for uncompresseddigital voice and G.729 codec for compressed voice. The bandwidth of themedia stream is relatively large compared to that of the signallingstream, for example the bandwidth of an uncompressed voice stream islikely to be 100 Kbps. Compression degrades audio quality in order toreduce the amount of data transmitted in order to reduced the amount ofbandwidth consumed by the call. However, compression usually corruptsDual Tone Multi-Frequency (DTMF) tones which have been sent over thevoice stream.

Historically this problem has been overcome by using ‘out of band’ DTMFwhereby DTMF tones are detected and sent using an uncompressed voicestream. Alternatively the DTMF data may be sent as separate packets inthe RTP stream.

More recently the data represented by the detected DTMF tone is sentover a SIP signalling stream associated with the voice stream.

b. Related Art

In United Kingdom patent application number 1604668.2 a secure datacollection system is described which uses an on demand appliance (ODA)in the contact centre to place a call out to a secure data collectionsystem whilst sensitive data is transmitted. The secure data collectionsystem prevents the sensitive data from reaching the agent. However, thesensitive data is routed through the ODA, which is located in thecontact centre, to the secure data collection system. Whilst anysecurity risk may be mitigated by physical security measures to preventaccess to the ODA it is undesirable for the sensitive data to ever passthrough the contact centre.

The separation of the signalling stream from the voice stream allows fora novel and inventive solution to the problem of processing sensitiveinformation over VoIP.

SUMMARY OF THE INVENTION

According to the invention there is provided a method of processing, bya call processor, a media call comprising the steps of: receiving afirst signalling stream from a first entity; creating a secondsignalling stream to a second entity; forwarding signals received fromthe first signalling stream to the second signalling stream; receiving athird signalling stream from the second entity; creating a fourthsignalling stream to the first entity; and forwarding signals receivedon the third signalling stream to the fourth signalling stream; thefirst signalling stream containing instructions to set up a media callbetween the first entity and the second entity such that media istransmitted over a first media stream from the first entity to thesecond entity and a media is transmitted over a second media stream fromthe second entity to the first entity without intervention by said callprocessor.

Preferably the media streams are redirected via the call processor, uponreceipt, by the call processor, of a message from the second entity themethod further comprising the steps of: the call processor sending amessage to the first entity to cause media to be transmitted over athird media stream to the call processor, the call processor creating afourth media stream and forwarding media received from the first entityvia the third media stream to the second entity over the fourth mediastream such that the call processor may modify the media received fromthe first entity before forwarding the media to the second entity; andthe call processor sending a message to the second entity to cause tocause media to be transmitted over a fifth media stream to the callprocessor, the call processor creating a sixth media stream andforwarding media received from the second entity via the fifth mediastream to the first entity over the sixth media stream such that thecall processor may modify the media received from the second entitybefore forwarding the media to the first entity.

In one embodiment the call processor modifies the media received fromthe first entity by removing sensitive information before forwarding themedia stream to the second entity.

In another embodiment the call processor modifies the media receivedfrom the first entity by removing DTMF tones before forwarding the mediastream to the second entity.

In a third embodiment the call processor modifies the media receivedfrom the first entity by removing spoken sensitive information beforeforwarding the media stream to the second entity.

Preferably the method further comprises the steps of: the contact centresending a message to a secure data collection centre to indicate securedata collection is to be initiated on a particular media call; thesecure data collection centre returning a personal identificationnumber; and in which the message received by the call processor from thesecond entity contains said personal identification number.

Advantageously the media streams are reconnected to bypass the callprocessor, the method further comprising the steps of the call processorsending a message to the first entity to cause the media to be sent overthe first media steam to the second entity; and the call processorsending a message to the second entity to cause media to be sent overthe second media stream to the first entity.

The first entity may be a user and the second entity may be a contactcentre.

The media call may be a VoIP call. The signalling streams may be SIPstreams. The media stream may be an RTP stream.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a call processing environment for use in asystem for collection of sensitive information;

FIG. 2 is a simplified illustration of call paths when a call is inunsecured mode;

FIG. 3 is a simplified illustration of call paths showing a callconferenced with the call processor;

FIG. 4 is a simplified illustration of call paths showing removal ofsensitive information from a media stream sent to a contact centre; and

FIG. 5 is a simplified illustration of call paths showing removal ofsensitive information from a media stream sent to a user.

DETAILED DESCRIPTION

Referring to FIG. 1, a call processor 14 is accessed via a firewall 11(eg AWS), and a Session Border Controller 12 (SBC) (eg AudioCodes orSonus). The call processor 14 interfaces with a secure data collectionenvironment 16.

A first entity, in the embodiment described here, a user 17 initiates aVoIP call to a second entity, in the embodiment described here, acontact centre 18. The VoIP call may originate from the PSTN via a trunkprovider. When the contact centre's address is detected in thesignalling stream (for example, when during call set up using a SIPINVITE message) the trunk provider redirects the signalling stream tothe call processor 14.

When call processor 14 receives a first signalling stream 20 from a user17 the call processor 14 creates a second signalling stream 21 to thecontact centre 18 and forwards any messages received via the firstsignalling stream 20 from the user to the contact centre 18 via thesecond signalling stream 21. Reciprocally the call processor 14 forwardsany messages received via a third signalling stream 22 from the contactcentre to the user 17 via a fourth signalling stream 23. The user isunaware that the signalling messages are intercepted and passed on bythe call processor 14. Hence once signalling messages are exchanged toset up a VoIP call between the user 17 and the contact centre 18 theVoIP call is created between the user 17 and the contact centre 18without intervention by the call processor 14. Hence, the bandwidth ofthe data that the call processor 14 needs to process is approximately 5Kbps×2. As the call processor 14 retains signalling paths to both theuser and to the contact centre the call processor 14 has the ability tocontrol the interaction between the user 17 and the contact centre 18.

In more detail, using SIP protocol the call set up process may be asfollows:

1) SIP INVITE (first call ID) is sent by the user 17 to the callprocessor 14.

2) SIP INVITE (second call ID) is sent by the call processor 14 to thecontact centre 18.

3) SIP OK (second call ID) is sent by the contact centre 18 to the callprocessor 14.

4) SIP OK (first call ID) is sent by the call processor 14 to the user17.

5) A first voice media stream 24 (usually using RTP) is created from theuser 17 to the contact centre 18.

6) A second voice media stream 25 (usually using RTP) is created fromthe contact centre 18 to the user 17.

FIG. 2 is a simplified illustration showing the signalling and mediastreams when the call is in an ‘unsecured’ mode ie when it is notrequired to transmit sensitive information between the user 14 and thecontact centre 17.

When it becomes necessary to transmit sensitive information between theuser 17 and the contact centre 18 a request 26, which may be initiatedby an agent in the call centre, is sent to the secure data collectionserver 16. The request 16 may be sent via the internet, via a privatenetwork or any other suitable means. The request from the contact centre18 contains a unique identifier (sometimes called a SessionID) thatidentifies the contact centre agent within the contact centre. Theunique identifier may be created (for example) when the contact centreagent logs onto the web interface of the Secure Data Collection 16system.

The Secure Data Collection 16 system generates a Personal IdentificationNumber (PIN) that is sends back to the contact centre agent over theInternet (typically displaying in a web browser).

The secure data collection server 16 returns a response 27 containing aunique identifier identifying the signalling streams and the media callin question.

The contact centre agent enters the PIN and generates a messagerequesting that a media call goes into ‘secure mode’ which is sent viasignalling stream 22 to the call processor 14. This message contains thePIN. Call processor 14 liaises with the secure data collection server 16to confirm that the request is legitimate, for example by comparing thePIN received to those which have been previously been sent out.

Assuming the request is legitimate call processor 14 reroutes the mediastream so that it is redirected via the call processor.

In more detail, using SIP protocol the call rerouting process may be asfollows:

1) re-INVITE (first call ID) is sent by the call processor 14 to theuser 17

2) SIP OK (first call ID) is sent by the user to the call processor 14

3) re-INVITE (second call ID) is sent by the call processor 14 to thecontact centre 18

4) Slp OK (second call ID) is sent by the contact centre 18 to the callprocessor 14.

The call processor 14 then initiates a conference call with the user 17and the contact centre 18. FIG. 3 is a simplified illustration of theresultant signalling and media streams.

A third VoIP media stream 30 is created between the user 17 and the callprocessor 14. VoIP data is transmitted over the third VoIP media stream30 to the call processor 14. The call processor 14 creates a fourth VoIPmedia stream 31 and forwards VoIP data received from the user 17 via theVoIP third media stream 30 to the contact centre 18 over the VoIP fourthmedia stream 31.

This will enable the call processor to modify VoIP data received fromthe user, for example by removing DTMF tones or spoken sensitiveinformation before forwarding the media to the contact centre 18.

FIG. 4 shows schematically sensitive data being removed from the fourthmedia stream 31 before being forwarded to the contact centre 18.

A fifth VoIP media stream 32 is created between the contact centre 18and the call processor 14. VoIP data is transmitted over the fifth VoIPmedia stream 32 to the call processor 14. The call processor 14 createsa sixth VoIP media stream 33 and forwards VoIP data received from thecontact centre 18 via the VoIP fifth media stream 32 to the user 17 overthe VoIP sixth media stream 33.

This will enable the call processor to modify VoIP data received fromthe contact centre 18, for example by removing DTMF tones or spokensensitive information before forwarding the media to the user 17.

FIG. 5 shows schematically sensitive data being removed from the sixthmedia stream 33 before being forwarded to the user 17.

The call processor 14 liaises with the secure data collection system 16to obtain the required sensitive data from the user 17 and removes thesensitive data from the media that is forwarded to the contact centre18, thus preventing the sensitive information from ever entering thecontact centre 18.

The call processor 14 only needs to process the bandwidth required forthe media call during the time that the call is in ‘secure’ mode. Oncethe sensitive data has been collected the media stream can bereconnected directly between the user 17 and the call centre 18 and thecall processor 14 will drop out of the media stream.

The call is rerouted in a similar manner to previously:

1) re-INVITE (first call ID) is sent by the call processor 14 to theuser 17

2) SIP OK (first call ID) is sent by the user to the call processor 14

3) re-INVITE (second call ID) is sent by the call processor 14 to thecontact centre 18

4) Slp OK (second call ID) is sent by the contact centre 18 to the callprocessor 14.

The call paths revert to those shown in FIG. 2.

It will be appreciated that features of the invention which are, forbrevity, described in the context of a single embodiment, may also beprovided separately, or in another suitable combination.

It will be recognised that various alterations, modifications, and/oradditions may be introduced into the constructions and arrangements ofparts described above whilst remaining within the scope of the inventionas claimed.

1.-11. (canceled)
 12. A call processor for processing a Voice overInternet Protocol (VoIP) media call comprising sensitive information,the call processor configured to at least: receive a first signallingstream from a first entity; create a second signalling stream to asecond entity; forward signals received from the first signalling streamto the second signalling stream; receive a third signalling stream fromthe second entity; create a fourth signalling stream to the firstentity; and forward signals received on the third signalling stream tothe fourth signalling stream; the first signalling stream containinginstructions to set up a VoIP media call between the first entity andthe second entity such that: (a) media comprising audio information istransmitted over a first media stream from the first entity to thesecond entity without intervention by the call processor; and; (b) mediacomprising audio information is transmitted over a second media streamfrom the second entity to the first entity without intervention by thecall processor; in which, when said sensitive information is to beincluded in said audio information, the call processor is configured toreceive a message from the second entity to reroute said media streamsso that these are redirected via the call processor, the call processorconfigured to: (i) send a message to the first entity to cause mediacomprising audio information to be transmitted over a third media streamto the call processor, create a fourth media stream to the second entityand forward media comprising audio information received from the firstentity via the third media stream to the second entity over the fourthmedia stream; and (ii) send a message to the second entity to causemedia comprising audio information to be transmitted over a fifth mediastream to the call processor, create a sixth media stream to the firstentity and forward the media comprising audio information received fromthe second entity via the fifth media stream to the first entity overthe sixth media stream; in which the call processor is configured tomodify media comprising audio information received from the firstentity, the call processor configured to remove sensitive audioinformation from said received audio information before said mediacomprising audio information is forwarded over the fourth media streamto the second entity; and in which the call processor is configured tomodify media comprising audio information received from the secondentity, the call processor configured to remove sensitive audioinformation from said received audio information before said mediacomprising audio information is forwarded over the sixth media stream tothe first entity.
 13. The call processor of claim 12, in which the callprocessor is configured to modify said received media by removing DTMFtones from the audio information before said media stream is forwarded.14. The call processor of claim 12, in which the call processorconfigured to modify said received media includes the call processorconfigured to remove spoken sensitive information from the audioinformation before said media stream is forwarded.
 15. The callprocessor of claim 12, in which the second entity is a contact centreconfigured to send a message to a secure data collection server toindicate secure data collection is to be initiated on a particular VoIPmedia call, and receive in return a personal identification number, andwherein the message received by the call processor from the contactcentre to reroute said media streams contains said personalidentification number.
 16. The call processor of claim 12, in whichafter said sensitive audio information has been transmitted in saidmedia streams, the call processor is further configured to at least:send a message to the first entity to cause said media to be sent overthe first media steam to the second entity; and send a message to thesecond entity to cause said media to be sent over the second mediastream to the first entity; whereby the media streams are reconnected tobypass the call processor.
 17. The call processor of claim 12, in whichthe first entity is a user.
 18. The call processor of claim 12, in whichthe signalling streams are SIP streams.
 19. The call processor of claim12, in which the first media stream is an RTP stream and the secondmedia stream is an RTP stream.
 20. The call processor of claim 12, inwhich the second entity is a contact centre.